home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941031-19941221
/
000072_news@columbia.edu_Tue Nov 8 00:00:10 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA11831
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 7 Nov 1994 19:00:14 -0500
Received: by apakabar.cc.columbia.edu id AA22323
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 7 Nov 1994 19:00:13 -0500
Path: news.columbia.edu!usenet
From: fdc@fdc.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: C-Kermit vs MS-Kermit
Date: 8 Nov 1994 00:00:10 GMT
Organization: Columbia University
Lines: 24
Message-Id: <39mf2a$lpf@apakabar.cc.columbia.edu>
References: <Pine.SUN.3.90.941106143639.22421D-100000@blue>
Nntp-Posting-Host: fdc.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <Pine.SUN.3.90.941106143639.22421D-100000@blue> "Archimedes L.
Trajano" <cs932070@ariel.cs.yorku.ca> writes:
> Is it not possible to create an MS-DOS version of Kermit from the
> C-Kermit source files?
>
Maybe, but why bother? It would be bigger, slower, and do less, except
for some of the script programming features. With some care, it is quite
possible to write script programs that are portable between MS-DOS
Kermit and C-Kermit. I'm not denigrating C-Kermit at all, but really,
when you consider how much functionality is packed into the 200K-or-so
MS-DOS Kermit executable, it's astounding.
For comparison, look at OS/2 C-Kermit, the closest C-Kermit counterpart
to MS-DOS Kermit. The 16-bit executable is 500K, and the 32-bit one is
680K. Although it might be unfashionable these days, there still is quite
a lot to be said for assembly language, especially when memory and
addressability are at a premium.
If somebody should really want to adapt C-Kermit to DOS, however, it should
be a mere matter of filling in some communications and file access primitives
and writing a terminal emulator. And hooking in to the various networking
APIs, if you can find them. Etc etc.
- Frank